Fix build: Use Sidekiq Explicit Configuration #45310
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Active Job tests for Sidekiq starts to fail since buildkite rails/rails/#87116 because Sidekiq 6.5.0 has API changes on how to configure Sidekiq. The new API does not accept hash anymore, so This Pull Request changes to how it is supposed to be configured (see here that a
config
is actually theSidekiq
module).After sidekiq/sidekiq#5225 / sidekiq/sidekiq#5329 is implemented, use the new
Sidekiq::Config
API.View Active Job Integration Test Failure
Summary
Fixes ActiveJob integration tests that failed to start Sidekiq worker due to Sidekiq API changes.